Ham Radio 2000 #1

home *** CD-ROM | disk | FTP | other *** search

/ Ham Radio 2000 #1 / Ham Radio 2000.iso / ham2000 / packet / digi37 / digiinfo.eng < prev next >

Wrap

Text File | 1994-09-02 | 21.1 KB | 496 lines

D I G I - I N F O V 3.7 ============================= Interlink- and Digipeater-Information (C) 1991-1994 by Patrick Sesseler, DF3VI ______________________________________________________________________________ Description: ============ DigiInfo is a program to inform about the packet network, written for IBM-PCs. In contrary to other programs (like HamMap) DigiInfo uses textmode. This makes it possible tu use DigiInfo as a remote-utility (run-program) for hostmode programms like SP or GP. Also only textmode makes it possible for blind packet users to get information about the network. DigiInfo offers the following features: - runs with any graphic adapter - uses standarised data-form (same data used for HamMap and others) - gives all (known) information about a station - lists all stations on a certain qrg - lists all stations in a locator-field - calculates the fastest route between two stations through the network - can route an alternative path if needed - can be started remote in some hostmode-programms - can "speak" different languages ______________________________________________________________________________ Informations: ============= DigiInfo was first based on the program DigiRoute by DG6KK, giving graphical network-information. By the time almost no routine stayed unchanged, lots were written completely new. Only the router remained almost unchanged, but this part is not by DG6KK originaly, but by Djikstra. The basic need of memory is dependant on the maximum of entrys the program can handle. So I compiled two different versions: - a normal version with 2500 stations and 6000 links - a big version for 5000 stations and 10000 links (requires more memory, so it may not run remoted anymore) For compiling the data into a better readable (for the computer, hi) form the program MAKEFST.EXE is needed. It compiles DigiInfo.STN (containing station data) and DigiInfo.LNK (containing link data) into DigiInfo.FST. MakeFst can be used for both memory versions of DigiInfo. If problems occure while compiling the data files a warning message will be displayed. Main problem is that HamMap-data are sorted wrong concerning station-SSIDs. For quick sorting these large files (and all other large files up to some MBs) i have written MegUSort.EXE. Simply call MegUSort <infile> <outfile>, where infile may be the same as outfile (overwriting the original file finally with the sorted). MakeFST can also compile HamMap-UPDATE-files. For this MakeFst is called with the name ob the update-file (a complete path may be added). First the old DigiInfo.STN file is read, then the stations are updated and the new DigiInfo.STN will be written to disk. After that the sme procedure will be done for the link update and a new DigiInfo.LNK will be written. MakeFST is called for multiple update-file each. After Updating SORT the new files (with MegUsort, see above) and than call MakeFST again without commandline parameter to compile the FST-file. ______________________________________________________________________________ Installation: ============= DigiInfo.EXE will be issued together with MakeFST and speak-files, all LHArced and 7PLUSsed. So you need 7PLUS and LHA to decode it. From version 3.5 on DigiInfo is multilingual (so for this reason it is spread EU-wide) and needs speak-files for text output. All speak-files are named DigiInfo and have a one or two letter extension indicating the language (by national prefix). Further prefixes for the same language can be related to a speak-file in DigiInfo.SPK (e.g. EI-stations will get english text, too). You will find more information about DigiInfo.SPK at the end of this documentation. Then you need of course DigiInfo.STN and DigiInfo.LNK, containing the data about stations and links. A smaller version (going with the normal sized version of DigiInfo) of this files is added to the program. If you want all data (and if you have enough memory for that!) you can use HamMap-data (since V4.0); just sort(!) Digi00.STN into DigiInfo.STN and Digi00.LNK into DigiInfo.LNK. More changes are not needed. Finally place program- and data-files to use DigiInfo as a remote program life this: - DigiInfo.EXE into the RUN-directory (also add that dir in the PATH in your AutoExec.BAT!) - MakeFst.EXE and MegUSort.EXE may be anywhere where you find it again, hi. But you should'n put it into the RUN-directroy... - ALL other DigiInfo.* files are put together in a directory that is indicated with SET DIGIDATA= path in your AutoExec.BAT. You can also set your own (WW)locator with SET OWNQTH= If you run DigiInfo just under DOS, you can put all files together into any directory you like (no change to AutoExec.BAT is needed then, but SET OWNQTH is still helpfull). Before DigiInfo can be started the first time you have to compile the FST-file with MakeFST. Just call MakeFST without any commandline parameter, but make sure you have about 500kB (or more) memory free. So normally you can't call MakeFst sucessfully in a secondary DOSshell. DigiInfo itselve needs less memory, with few data a minimum of 150kB is required; more data can require up to 400kB. After all that DigiInfo can be executed as remote ( //DIGIINFO in SP or GP, RUN DigiInfo in TheBox 1.9) as by yourself (SP: Enter <ESC> !DIGIINFO ... , GP: <ESC> //RUN DIGIINFO ...). Normal calling from the DOS-prompt is of course possible, too. A hint for GP-users (V1.50 and later): Calling <ESC> //DIGIINFO without commandline parameters will NOT give a help-screen (unlike to calling via DOS), but a message that this is not possible! If you need help call <ESC> //DIGIINFO /? . A hint for DR-DOS-User (and also other SHELL-users): If you start your programs from the shell surface, the SET-lines must be placed BEFORE the call of the shell programm (best place them at the beginning) in your AutoExec.BAT file. Otherwise (SET-lines at the end) the SET-lines will never be executed! ______________________________________________________________________________ How to use DigiInfo: ==================== a) conventional execution (witt commandline parameters): Because calling remote programs gives no possibility for additional entrys later on all needed parameters must be entered immediately. The program detetcs the requested function by interpreting the parameter(s). - NO parameter : Gives a short help (not in GP 1.50 and later, see part (b) below). - ONE parameter: = freqency: All stations listed on that frequency in DigiInfo.STN well be displayed (also if you just enter MHz, than all on this MHz will be shown). = callsign: All available information (QTH, QRG etc.) to that call will be displayed, the geographical coordinates calculated (if loactor is known), and all links (with distance, heading, speed) listed. = Prefix: All call signs with the appropriate prefix will be displayed (when calling DigiInfo remote a prefix must consist of at least two characters!). NEW: = Locator-field (e.g. JN39): All Stations inside the locator-field are listet together with status, frequency and locator, if they are qrv and have an user-qrg. Also distance and heading from the locator defined with SET OWNQTH are calculated. = QTH-locator: Is calulated into degree-coordinates. Additionally distance and heading to the locator defined with OWNQTH are calculated (if defined, hi). = /Option: /STAT: Gives summary about memory consuption etc. /? : Gives short help. / : "empty Option", only copyright well be displayed. /L:x : Switches to language "x" (one or two letters). Hint: You can just enter ONE option at a time. You cannot enter more parameters together with an option! - TWO parameters: The fastest (shortest) route between the two given stations is calculated. Hint: DigiInfo only routes via digipeaters and nodes, but not via BBSes, DXCluster or unknown systems. If digipeater or links failed or are not active you can exclude them from the routing --> - More than two parameters: No routing via the given links or digipeaters. Up to 15 exclusions are possible in commandline (more in a file DigiInfo.N_V, see later). A link-exclusion is ONE parameter though needing TWO calls, the calls are seperated by a slash ( / ), not a space! Example: I want to know the Route from DB0HOM to ON7RC; the link fron DB0DIG to DB0GE is not available and ON5ZS is not active at all. Then I enter: > DIGIINFO DB0HOM ON7RC DB0DIG/DB0GE ON5ZS SP only: If you add an upcase "C" as very last parameter when routing a SP-compatible connectfile is written. This can be read into SP by CTRL-L and then send out line by line. The filename is the destination call and the extension is .C . (This function is NOT remoteable under SP, because SP adds three additional parameters; these are not used but for getting the prefix of the caller. You can use it only with ESC! DIGIINFO ... C . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - b) Execution as GPRI-programm (since GP V1.50), without parameter: After calling //DIGIINFO the programm installs itself resident in memory. The caller gehts an menu surface and has to enter instruction (as in a BBS system). The menu has two levels (similar to some server functions in FBB-bbs): In the highest level you can choose under the following functions: Info : Switch to Menu for information about callsing, frequencies etc... Route: Switch to Menu for routing from station to station Stat : Statistics about memory usage Lang : Changing the language Quit : Terminate DIGI-INFO Inside the ROUTE-Menu exist the following instructions: Call : All informationen about Call Prefix: List of Calls with prefix Freq : List of Calls on QRG Loc : Locator-filed search or calculation WW-Locator to Degree Main : Back to main menu Inside the INFO-Menu exist the following instructions: Start : StartCall for routing End : Dest.Call for routing and calculating route Not_Via: Exclude digi <Call> or link <Call1/Call2> with new calculation of route. Up to 15 Not-VIAs are possible ! Clear Not_Via-List with entry input. Main : Back to main menu If an instruction needs an additional parameter (e.g. a callsign) it is asked for interactive. The parameter can also added directly to the instruction, seperated by a space). ______________________________________________________________________________ EXAMPLES: ========= a) conventional: CALL: (Remote with //...) Output: ----- ------- DIGIINFO Gives short help. DIGIINFO /STAT Gives memory consuption etc. DIGIINFO /L:D Switches to german language (Not remoteable by SP/TheBox) (if DigiInfo.D is found). DIGIINFO 144. Lists all calls un 2m. DIGIINFO 438.150 Lists all calls on that QRG. DIGIINFO JN39 Lists all calls in that locator-filed if they are accessible direct. DIGIINFO JN39PH Converts locator into coordinates and calculates distance to OWNQTH. DIGIINFO OE9 Lists all known calls staring with OE9: OE9XFR, OE9XPI, OE9XPR ... DIGIINFO DB0HOM Shwos everything known about DB0HOM (QTH, user-QRG, Links etc.) DIGIINFO DB0GE OE9XPR Calculates fastest route from DB0GE to OE9XPR: DB0GE <4K8> DB0DQ <1K2> HB9EAS <1K2> OE9XPR DIGIINFO DB0GE OE9 Calculates all routes from DB0GE to OE9 (maximum of 9). DIGIINFO DB0GE OE9XPR DB0DQ Calculates route from DB0GE to OE9XPR not running via DB0DQ: DB0GE <9K6> DB0DIG <9K6> DB0ORT <9K6> FF6KDL <9K6> HB9EAS <1K2> OE9XPR DIGIINFO DB0GE OE9XPR HB9EAS/DB0DQ Calculates route from DB0GE to OE9XPR, not running via link DB0DQ/HB9EAS: DB0GE <4K8> DB0DQ <1K2> DB0HP <1K2> OE9XPR As you see sometimes it can be better to exclude just a link instead of a digipeater. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - b) Using DigiInfo as GPRI: Input: Output: ------ ------- //DIGIINFO Starts DigiInfo, geves a promt asking for input: Stat Gives memory consumtion etc. Help Gives short help about main menu. Info Switches to INFO-menu Help Gives short help about Info-menu Lang D Switches to german language (if DigiInfo.D is found). Freq 144. Lists all calls un 2m. Freq 438.150 Lists all calls on that QRG. Loc JN39 Lists all calls in that locator-filed if they are accessible direct. Loc JN39PH Converts locator into coordinates and calculates distance to OWNQTH. Call OE9 Calculates all routes from DB0GE to OE9 (maximum of 9). Call DB0HOM Shwos everything known about DB0HOM Main Back to main menu Route Switches to Route-Menue Help Gives short help to Route-menu Start DB0GE Set start call for Routing End OE9XPR Set destination call and calculate fastest route from DB0GE to OE9XPR Not_via DB0DQ Adds DB0DQ into Not_Via-list and calculates fastest route that does not run via DB0DQ Not_via HB9EAS Adds HB9EAS to Not_Via-list hinzu and calculate fastest route running neither via DB0DQ nor HB9EAS Not_via A RETURN as an empty input cleares the Not_Via-list (also the not-vias listed in DigiInfo.N_V) Not_via DB0DQ/HB9EAS Adds link DB0DQ-HB9EAS in Not_Via-list and calculates fastest route that does not run via link DB0DQ-HB9EAS Quit Terminate DigiInfo Some more hints: - The output is as calling the program conventional (in general, hi) - It is enough to enter the UPCASE letters of an instruction (normally just the first letter) - several instructions can be seperated by SPACE (up to six), but after a parameter nothing may follow! - changing from rout- to main-menu and back erases Not_Via-list, but NOT the not-vias listed in DigiInfo.N_V. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - c) Data-update with MAKEFST: (MAKEFST should NOT be remoted or started within a shell) If you want to update with DIGI01.UPD and DIGI02.UPD, placed in E:\HAMMAP\STN\UPD, make the following calls at the primary DOS-promt: MAKEFST E:\HAMMAP\STN\UPD\DIGI01.UPD MAKEFST E:\HAMMAP\STN\UPD\DIGI02.UPD MEGUSORT DIGIINFO.STN DIGIINFO.STN MEGUSORT DIGIINFO.LNK DIGIINFO.LNK MAKEFST Calling MEGUSORT is not needed if MakeFST runs without warnings. Never forget the final call of MakeFST without parameters, compiling the FST-file! MAKEFST should NOT be called in a secondary DOS-SHELL if not at least 500kb of memory is available. ______________________________________________________________________________ Routing quality: The quality given to a route is simmilary to the well known NetRom quality (but not the same!). The link speed counts as follows: <---> : 99% (wired link) <19200> : 99% <9600> : 98% <4800> : 95% <2400> : 92% <1200> : 90% <>-X-<> : 0% (Link not QRV) Routes with qualitis down to 70% are quite fast (normally), down to 50% mostly good usable, but below that you often need a good portion of patience, hi. If a route leads via a not active link or digipeater, the quality becomes zero and is not shown anymore. Additionaly to any route the total link-length and also ditance and heading between star- and destination will be calculated, if all locators of the stations in the path are known! ______________________________________________________________________________ Special files: - DigiInfo.N_V If digipeaters or links are not active for some time, but you don't want to active the station resp. link data, you can enter these as exclusion into this file DigiInfo.N_V . The file must be placed in the same directory as all the other DigiInfo files are, or it will not be found. The form of the file is simplest, just enter the exclusions one in a line (example): 1st Line: ON5ZS 2nd Line: DB0AAC/DB0AAI 3rd Line: Here one link and one station is excluded. The file is terminated with an empty line! - DigiInfo.SPK (and speak-files) From Version 3.5 on DigiInfo can make output in several languages. Under SP/DieBox and as GPRI the language is extracted automatically from the call of the user. For prefixes that have no own language file you can enter what language should be used for them in DigiInfo.SPK . Also the default language for use under DOS (and OLD GP before V1.50 as other programs that give no callsign in commandline) is entered here. DigiInfo.SPK is made as follows: 1st line: G default language 2nd line: LX=F french text for luxemburges 3rd line: ON=F and belgium users 4th line: PA=G english text for netherlands 5th line: PE=G 6th line: OE=D german text fpr austrian 7th line: HB=D and swiss users 8th line: empty line! On the left side of the equation sign stands the desired prefix, on the right side the extension of the speak file. both sides consist of one or two charactes each. The speak file for the default language MUST be available, otherwise DigiInfo cannot start! A quite complete DigiInfo.SPK and speak files for DL, F and G are added to the program. The speak files and DigiInfo.SPK must of course be placed in the same directroy set with DIGIDATA (ass all DigiInfo files). The files are normal text so you can edit them if other translation needed. But be careful that neither lines are added nor deleted, empty lines must stay empty. Where variables are inserted into the lines it is indicated with square brackets []. Also this sign must be unchanged. If a language is selected but no speak file found the default language will be activated. Running as GPRI the language can be changed with the "lang"-command. Under DOS it is changed with DIGIINFO /L:x (where "x" is the desired language), which also changes the default language. Under SP and TheBox this command is disabled when called remote. ______________________________________________________________________________ Final remarks: The program was tested as good as possible, and i hope that no severe errors (apart from lack of memory, hi) will occure. Because of the increased amount of data the needed memory has increased, too. So the use as remote program may be difficult. If you any other problem, just ask me. I'll try to answer within a week (plus forwarding time!). /_/_/__/__/__/__/ vy 73 *** / / / /! / / / & * * ! 55 de Patrick, DF3VI @DB0HOM.#SAR.DEU.EU ! * * DOK Q07 ! Loc. JN39PH ***